Docker Techstack Rolldev Mcp Server

Created By
RollDev Team & Disrex E-commerce & Hosting10 months ago
MCP server for Roll Docker Stack and multi-framework development environments.
Overview

📝 RollDev MCP Server – Summary

The RollDev MCP Server is a bridge between Roll Docker Stack and LLMs (Claude, etc.) via the Model Context Protocol (MCP). It lets AI agents interact directly with your Docker-based development environments.


✅ Key Capabilities

  • Environment management → list, start, and stop RollDev project environments

  • Service control → manage system services like MySQL, Redis, Elasticsearch, RabbitMQ, Varnish

  • Project initialization → create new projects (Magento, Laravel, Symfony, TYPO3, Shopware, WordPress, Akeneo, PHP) with auto-configuration

  • Development utilities:

    • Run SQL queries in project databases
    • Execute PHP scripts inside containers
    • Access framework CLI commands (bin/magento, artisan, bin/console, etc.)
    • Run Composer commands for dependency management

🚀 Why it matters

  • Turns Roll Docker Stack into an AI-controllable dev environment
  • Saves time by letting LLMs query databases, run CLI tasks, and manage services without leaving chat
  • Works across multiple frameworks (not just Magento 2)

👉 In short: It’s an AI-powered control layer for RollDev environments — giving you hands-free project setup, service control, and development automation.

Server Config

{
  "mcpServers": {
    "rolldev": {
      "command": "npx",
      "args": [
        "-y",
        "@disrex/rolldev-mcp-server"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
RollDev Team & Disrex E-commerce & Hosting
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 minutes ago